## Differences Between 9600 Series and 4600 Series IP Telephones

Review this section if you administer both 4600 and 9600 Series IP Telephones.

Signaling - 46xx Series IP Telephones can use H.323 or SIP for telephony signaling. 96xx Series IP Telephones only use H.323. SIP-related administration of 96xx telephones is neither necessary nor relevant.

Avaya Communication Manager Release - 46xx telephones are supported prior to Communication Manager Release 3.0. The 96xx telephones are not officially supported prior to Release 3.0.

DHCP & SSON - 46xx telephones use Option 176 as the default DHCP Site Specific Option Number (SSON); 96xx telephones use Option 242.

Upgrade Script - The upgrade script files have different names and content (“46xxupgrade.scr” versus “96xxupgrade.txt”).

File Servers - 46xx telephones can use either TFTP or HTTP servers as file servers, for example, to download new phone firmware, upgrade script files, or settings files. 96xx telephones only use HTTP.

Backup - 46xx telephones use FTP as the protocol to create and access backup files. Users can specify unique backup server addresses, backup directories, FTP User IDs, and FTP User Passwords. 96xx telephones use HTTP as the protocol to create and access backup files, and users have no options to change backup parameters. 96xx telephones use the settings file parameter BRURI to identify the backup file site.

Backup Filenames - 96xx telephones store their backup files with titles that do not include the model number, for example, 1234_96xxdata.txt vs. 1234_4610data.txt or 1234_4620data.txt.

Backup File Content - Backup file contents are generally the same, except that the 96xx Contacts data is stored as:

ABKNAME mmm = label
ABKNUMBER mmm = telephone number
ABKTYPE mmm = entry type

where mmm is 001 to 250. A given Contact entry in the 96xx Backup file must have both name and number to be valid. Type is optional. ABK stands for “Address Book”, the original Contacts application name.

Settings File - Although both 46xx and 96xx telephones use the 46xxsettings file, the 96xx uses the following new parameters:

BRURI - to specify a URI to place the backup file
HTTPDIR - to specify a subdirectory path on the HTTP server
MSGNUM - for voice mail access
UNNAMEDSTAT - to turn Unnamed Registration off/on

Any 46xx telephone receiving these 96xx-specific parameters ignores them.

IR/SMTP - 96xx telephones do not support Infrared (IR) or Simple Message Transport Protocol (SMTP), so any such 46xx administration is ignored.

Local Administration - The 46xx QOS, CTI, and ALERT Local Procedures are not supported by the 96xx telephones. Also, there is no indication of IR interfaces in the INT Local Procedure.

Language - 96xx telephones do not presently support language administration. The user interface supports only English.

SNMP & MIBs - Although both 46xx and 96xx telephones support SNMP v2c and have custom Management Information Bases (MIBs), the MIBs are formatted somewhat differently.

Wideband Codecs - 96xx telephones support G.722 (wide band) codecs, unlike 46xx telephones.

Feature Button Administration - Although 96xx telephones do not require administration of the following feature buttons, the user experience is enhanced if they are administered: Conference Display, Selective Conference Party Mute, Send All Calls (SAC).